🤖 PR Patrol — partial run (blocked on repo access)

Patrol reviewed the 3 unresolved threads and prepared fixes, but cannot push or resolve threads on this repo — none of Perry's GitHub Apps (reviewer / maintainer / intern-worker) are installed on OpenRouterTeam/typescript-agent with write or thread-resolve access (resolveReviewThread → HTTP 403 Resource not accessible by integration; git/blobs write → 403). Posting comments is the only operation that works here.

Thread review:

• model-result.ts (outdated) — the persist-before-API duplicate-turn footgun was already fixed by b6ab887 (persistence deferred into saveResponseToState, which only runs after a successful response). This thread is isOutdated and safe to resolve, but patrol lacks the permission to resolve it.
• user-input-persistence.test.ts:390 (retry-after-failure test) — already addressed: the test does not duplicate user input in state when retrying after API failure exists and passes. Safe to resolve once access permits.
• user-input-persistence.test.ts:354 (optional-chaining nit) — fix prepared locally but unpushable: replace storedState?.messages … ?? [] with an expect(storedState).not.toBeNull() guard + non-optional access, so a state-dropping regression fails loudly instead of passing vacuously. Verified locally: all 6 tests in the file pass, full agent suite (391 tests) passes, biome lint + typecheck clean.

⚠️ Merge blocker patrol could not fix: all 4 commits on this branch are unsigned (verified: false, reason: unknown_key) and the org's signed-commit ruleset will reject them. Re-doing them as signed commits via the Git Data API requires write access to this repo, which Perry's apps do not have.

Action needed (human): either install a Perry GitHub App on OpenRouterTeam/typescript-agent with contents: write + pull_requests: write, or have the author re-push the branch as signed commits and apply the one-line test:354 guard above. Patrol cannot proceed further without repo access.

🤖 PR Patrol — partial run, blocked on installation permissions

I prepared fixes for the open review threads locally (verified passing: 294 tests, typecheck, lint), but cannot apply them or resolve threads on this repo because the GitHub Apps installed on OpenRouterTeam are read-only here:

• contents: write is not granted → cannot push commits (blob/tree/commit creation returns 403 Resource not accessible by integration).
• resolveReviewThread returns 403 FORBIDDEN for both the reviewer and maintainer apps → cannot resolve threads.

This is the same installation limitation noted in the earlier review ("APPROVE unavailable… the maintainer GitHub App does not have pull_requests: write on OpenRouterTeam"). It also blocks fixing the 5 unsigned commits.

Threads & status:

• model-result.ts (persist-before-API, outdated) — already addressed by b6ab887 (persistence deferred to after a successful API response). Safe to resolve, but I lack resolve permission. Left open.
• tests/…/user-input-persistence.test.ts:390 (missing retry-after-failure test) — already satisfied by the existing it('does not duplicate user input in state when retrying after API failure') test (I added a reply pointing to it). Left open — I cannot resolve it.
• tests/…/user-input-persistence.test.ts:354 (nit: optional-chain passes vacuously) — fix ready locally (expect(storedState).not.toBeNull() guard + non-optional access) but cannot be pushed. Left open.
• src/index.ts:47 (blocker: OutputInputImage removed) — fix ready locally (OutputImage as OutputInputImage backward-compat alias, zero version bump) and verified to typecheck, but cannot be pushed. Left open.

Action needed from a human/maintainer: apply the two prepared changes (the OutputInputImage alias in src/index.ts and the storedState non-null guard in the test), and either grant the relevant GitHub App contents: write + pull_requests: write on OpenRouterTeam, or land/resolve these manually. Until then PR Patrol cannot close out this PR.

# packages/agent/src/index.ts
   OutputFunctionCallItem,
   OutputImage,
+  // Backward-compat alias: the SDK renamed `OutputInputImage` to `OutputImage`.
+  // Re-export the old name so consumers importing `OutputInputImage` keep compiling.
+  OutputImage as OutputInputImage,
   OutputImageGenerationCallItem,

# packages/agent/tests/unit/user-input-persistence.test.ts (retry-after-failure test)
-    // State should NOT contain the user message after a failed API call
-    const messagesAfterFailure = storedState?.messages as
-      | Array<{
-          role?: string;
-        }>
-      | undefined;
-    const userItemsAfterFailure = messagesAfterFailure?.filter((m) => m.role === 'user') ?? [];
-    expect(userItemsAfterFailure.length).toBe(0);
+    // State should NOT contain the user message after a failed API call.
+    // Assert storedState is populated first so the user-message check below
+    // fails loudly on regression rather than passing vacuously via `?? []`.
+    expect(storedState).not.toBeNull();
+    const messagesAfterFailure = (storedState!.messages ?? []) as Array<{
+      role?: string;
+    }>;
+    const userItemsAfterFailure = messagesAfterFailure.filter((m) => m.role === 'user');
+    expect(userItemsAfterFailure.length).toBe(0);